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

Correct Postgresql engine version #1580

Merged
merged 7 commits into from
Jun 23, 2020

Conversation

zzxwill
Copy link
Member

@zzxwill zzxwill commented May 27, 2020

Description of your changes

Fix issue crossplane-contrib/provider-alibaba#23

How has this code been tested?

Checklist

I have:

  • Run make reviewable to ensure this PR is ready for review.
  • Ensured this PR contains a neat, self documenting set of commits.
  • Updated any relevant documentation and examples.
  • Reported all new error conditions into the log or as an event, as
    appropriate.

For more about what we believe makes a pull request complete, see our
definition of done.

Followed provision infrasture to provision an RDSInstance CRD,
it failed with the issue connect failed: cannot get provider
secret: Secret "alibaba-creds" not found. By creating the secret
in namespace `crossplane-system` will fix the issue

Signed-off-by: zzxwill <zzxwill@gmail.com>
allowed engine version should among 9.4/10.0/11.0/12.0

Signed-off-by: zzxwill <zzxwill@gmail.com>
@zzxwill zzxwill changed the title Postgresql engine version Correct Postgresql engine version May 27, 2020
@zzxwill zzxwill closed this May 27, 2020
@zzxwill
Copy link
Member Author

zzxwill commented May 27, 2020

Please hold on, this modification might affect the engine version for AWS/GCP/Azure, sorry. Let me think it over.

@zzxwill zzxwill reopened this May 27, 2020
@muvaf
Copy link
Member

muvaf commented Jun 2, 2020

As @hasheddan pointed out, claims are to be deprecated. But we're still supporting them. I think we can get rid of this whole list altogether. If an unsupported version is used, provider will return an error anyway. @zzxwill removing the line here and running make reviewable should take care of this. You can do so for MySQLInstance as well by removing this line.

@zzxwill
Copy link
Member Author

zzxwill commented Jun 4, 2020

As @hasheddan pointed out, claims are to be deprecated. But we're still supporting them. I think we can get rid of this whole list altogether. If an unsupported version is used, provider will return an error anyway. @zzxwill removing the line here and running make reviewable should take care of this. You can do so for MySQLInstance as well by removing this line.

Got it. I will push another commit. Thanks.

…-version

Merge upstream/master to fix branch

Signed-off-by: zzxwill <zzxwill@gmail.com>
As CRD manifest is generated by go module, so revert previous
change on the manifest and remove engine version constrains.

Signed-off-by: zzxwill <zzxwill@gmail.com>
- "10.0"
- "11.0"
- "12.0"
- "9.6"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did you run make reviewable after removing the validation line? I'd expect the enum array here to go away automatically since CRDs are deleted and regenerated via make reviewable

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No. But I did just now following with another commit. Thank you, now I learnt the mechanism.

Signed-off-by: zzxwill <zzxwill@gmail.com>
Signed-off-by: zzxwill <zzxwill@gmail.com>
Copy link
Member

@muvaf muvaf left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@muvaf muvaf requested a review from hasheddan June 23, 2020 10:25
@muvaf muvaf merged commit 4d8071a into crossplane:master Jun 23, 2020
@zzxwill zzxwill mentioned this pull request Jul 20, 2021
6 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants