Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workaround for non-existent GH repo tags. #6221

Merged
merged 1 commit into from
Apr 20, 2023
Merged

Conversation

absoludity
Copy link
Contributor

Description of the change

See #6220 for a description.

Benefits

We can release.

Possible drawbacks

We'll need to manually update the auto-generated PR for the upstream change with the correct images.

Applicable issues

Additional information

@netlify
Copy link

netlify bot commented Apr 20, 2023

Deploy Preview for kubeapps-dev canceled.

Name Link
🔨 Latest commit 378e8fe
🔍 Latest deploy log https://app.netlify.com/sites/kubeapps-dev/deploys/6440bf256db9e70008a3d6fd

@absoludity absoludity merged commit 77155ab into main Apr 20, 2023
@absoludity absoludity deleted the workaround-for-6220 branch April 20, 2023 04:27
absoludity added a commit that referenced this pull request May 1, 2023
<!--
Before you open the request please review the following guidelines and
tips to help it be more easily integrated:

 - Describe the scope of your change - i.e. what the change does.
 - Describe any known limitations with your change.
- Please run any tests or examples that can exercise your modified code.

 Thank you for contributing!
 -->

### Description of the change

After getting a couple of dev chart auto-created PRs like #6236, which
are doing nothing except setting our development images from `latest`
(which they should be in the dev chart) to a fixed version, I realised
that in #6221 I'd actually updated the incorrect part of the script.

This PR fixes that, by ensuring that we don't refer to `tag` in
`replaceImage_latestToProduction` since we don't have the production
values of the tag currently (until we update to use the dockerhub API as
per #6220) - this was the intended change of the previous PR - and
reverts the unintended change that updated
`replaceImage_productionToLatest` so that we again expect `latest` for
our own images in the dev chart.

### Benefits

<!-- What benefits will be realized by the code change? -->
We're no longer bothered by noop PRs such as #6236 .

### Possible drawbacks

<!-- Describe any known limitations with your change -->

### Applicable issues

<!-- Enter any applicable Issues here (You can reference an issue using
#) -->

- fixes #

### Additional information

<!-- If there's anything else that's important and relevant to your pull
request, mention that information here.-->

Signed-off-by: Michael Nelson <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants