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 the helm deployment output. #109

Closed
tsaxena18 opened this issue Sep 7, 2020 · 2 comments · Fixed by #113
Closed

Correct the helm deployment output. #109

tsaxena18 opened this issue Sep 7, 2020 · 2 comments · Fixed by #113
Assignees

Comments

@tsaxena18
Copy link
Collaborator

tsaxena18 commented Sep 7, 2020

With the configurations set in values.yaml for cluster provider, cache provider, store, etc. we do helm deployment and get the last statement of output as :
Your release is named fdsa600app. and deployed in openshift with FTL mode.

FTL is a cluster provider and when we talk about mode in context with BE its usually a persistence or OM options.
So if my setup is OpenShift as cloud platform, FTL as cluster provider and Store as OM then the statement should come as :
Your release is named fdsa600app. and deployed in OpenShift with FTL as cluster provider and mode as 'Store'.

@tsaxena18
Copy link
Collaborator Author

  1. For all the AS2x clustered cases we get,
    Your release is named fdc600app. and deployed in azure with AS2 mode

  2. For all the FTL clustered cases we get,
    Your release is named fdc600app. and deployed in azure with FTL mode

  3. For unclustered case we get,
    Your release is named fd600app. and deployed in azure with unclustered mode

So there are only 3 types of output. Now change should be to also include the mode as None, Store, etc.

@nareshkumarthota
Copy link
Collaborator

The notes text can be modified like below mentioned. I think this serves the purpose.
Your release is named {{ .Release.Name }}. and deployed in {{.Values.cpType}}. Cluster Type: {{.Values.cmType}}. OM Type: {{.Values.omType}}.

This issue was closed.
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 a pull request may close this issue.

2 participants