You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was thinking about how instance types are not updated until the next refresh and once we've merged #752, I wonder if those values can be pulled live from this repo during refresh, or perhaps on demand. I haven't worked out all of the details in my head, but some points I'm thinking:
We would need to include a version number or flag or something in the yaml file and/or permanently ensure backward compatibility.
Since it's unlikely to update that frequently we might want to use an ETag to avoid pulling something that hasn't changed.
Failure to fetch, update, anything would gracefully write a log message and move on.
Users should be able to "opt-out" or "opt-in" in case they are deploying into a DMZ and don't want to be pulling from github.com
The text was updated successfully, but these errors were encountered:
This issue has been automatically marked as stale because it has not been updated for at least 3 months.
If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.
Thank you for all your contributions! More information about the ManageIQ triage process can be found in the triage process documentation.
I was thinking about how instance types are not updated until the next refresh and once we've merged #752, I wonder if those values can be pulled live from this repo during refresh, or perhaps on demand. I haven't worked out all of the details in my head, but some points I'm thinking:
The text was updated successfully, but these errors were encountered: