Skip to content

[DGS-4331] make sr cluster upgrade consistent#1383

Merged
Anshul Goyal (Anshul-Goyal) merged 3 commits intomainfrom
DGS-4331
Aug 5, 2022
Merged

[DGS-4331] make sr cluster upgrade consistent#1383
Anshul Goyal (Anshul-Goyal) merged 3 commits intomainfrom
DGS-4331

Conversation

@Anshul-Goyal
Copy link
Contributor

Checklist

  1. [CRUCIAL] Is the change for CP or CCloud functionalities that are already live in prod?
    • yes: ok

What

Updating error message for schema-registry cluster upgrade consistent with the success message.

References

https://confluentinc.atlassian.net/browse/DGS-4331

Test & Review

Tested locally against stag.

SRInvalidPackageType = `"%s" is an invalid package type`
SRInvalidPackageSuggestions = "Allowed values for `--package` flag are: %s."
SRInvalidPackageUpgrade = `Schema Registry already uses "%s" package`
SRInvalidPackageUpgrade = "Environment \"%s\" is already using the Stream Governance \"%s\" package.\n"

Choose a reason for hiding this comment

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

Suggested change
SRInvalidPackageUpgrade = "Environment \"%s\" is already using the Stream Governance \"%s\" package.\n"
SRInvalidPackageUpgrade = "Environment \"%s\" is already using Stream Governance package \"%s\".\n"

Copy link
Contributor Author

Choose a reason for hiding this comment

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

In the UI, we're using the following messages -
Enable your Stream Governance essentials package or Upgrade to Stream Governance advanced package

So, I guess Environment "env-12345" is already using the Stream Governance "essentials" package. might be more consistent than Environment "env-12345' is already using Stream Governance package "essentials"

wdyt?

Copy link

@brianstrauch Brian Strauch (brianstrauch) Aug 4, 2022

Choose a reason for hiding this comment

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

I just suggested this since this is the wording we use for all of our other resources. Examples:

Deleted kSQL cluster "lksqlc-12345".

Error: failed to delete API key "123456789"

I'm not too picky though and I could see this going either way. Up to you and your team!

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.

3 participants