You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2021/07/28 07:57:49 UTC

[GitHub] [airflow] potiuk commented on pull request #17282: Chart: Add instructions to Update Helm Repo before upgrade

potiuk commented on pull request #17282:
URL: https://github.com/apache/airflow/pull/17282#issuecomment-888098780


   Just to explore it still @kaxil. 
   
   I am not convinced what is the best way. I still think we CAN publish index with .yaml with "archives", it's just important what is the timing of this publishing.
   
   From what I saw, the delays of copying "downloads" to "archives" is small (I believe it is less than hour always from earlier discussions). In fact, the release policy of ASF specifically mentions: "downloads.apache.org is automatically archived. Therefore, a copy of an official release will already exist in the archives. To move a release to the archives, just delete the copy in your project's dist directory. Remember to update any links from the download page." 
   
   And I think it is in our hands to delay publishing the new `index.yaml` whenever we save chart to the repository. We have two options:
   
   * we could wait with publishing the new index.yaml until "archives" copy is available (and make announcements an hour later).
   * we could also make it a  "stage" publishing - ie. publish "downloads" link together with SVN update, and automatically replace it with "archives" when the archive copy is available
   
   I think both scenarios provide "uninterrupted" use of helm chart and we can fully automate both of those scenarios. And also prevent our users the surprises like https://apache-airflow.slack.com/archives/C027H098M1C/p1627440863116600 where it basically invalidates the old index you already have locally cached. The error message in this case is not telling too much and I think there is a benefit with having the "stable" links to download the charts.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@airflow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org