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

feat(provider/google): Added Cloud Run manifest functionality in Deck. #9971

Merged
merged 6 commits into from
May 1, 2023

Conversation

siddhu-opsmx
Copy link
Collaborator

This is part of spinnaker/governance#302

Added Cloud Run manifest functionality in Deck.

@siddhu-opsmx
Copy link
Collaborator Author

@mattgogerly could you please review the PR

{statusKey}
</span>
)}
{(isStable || isUnstableWithMessage) && <span>&nbsp;</span>}
Copy link
Member

Choose a reason for hiding this comment

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

I'm not sure this does anything useful?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Removed unwanted condition check

Copy link
Member

Choose a reason for hiding this comment

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

This seems to duplicate the Kubernetes equivalent. Can we generify that instead of having the same code twice?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Yes , for now we are using this component in 2 modules (i.e, Kubernetes and Cloud Run) and we can generify that as well But in future if Kubernetes modifies the component based on some new requirement will affect Cloud Run module as well or vice-versa. So we are trying to keep the scope of components to module-centric, So that modification in any one module will not affect other modules.

import type { IDeploymentStrategy } from '@spinnaker/core';

export const strategyRedBlack: IDeploymentStrategy = {
label: 'Red/Black (Deprecated)',
Copy link
Member

Choose a reason for hiding this comment

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

Why is red/black deprecated?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Corrected label text.

@@ -5,6 +5,7 @@ export interface IArtifactTypePatterns {
export const ArtifactTypePatterns: IArtifactTypePatterns = {
BITBUCKET_FILE: /bitbucket\/file/,
CUSTOM_OBJECT: /custom\/object/,
CLOUDRUN: /cloudrun\/(.*)/,
Copy link
Member

Choose a reason for hiding this comment

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

Forgive me if I'm not familiar with Cloud Run. Why does it have its own artifact type if the manifest is just YAML/JSON?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

So based on back-end implementation CLOUDRUN type is not much useful for now like KUBERNETES, So removing it for now will add it if required in future based on enhancement request .

@j-sandy j-sandy added the ready to merge Reviewed and ready for merge label May 1, 2023
@mergify mergify bot added the auto merged Merged automatically by a bot label May 1, 2023
@mergify mergify bot merged commit f5e19c7 into spinnaker:master May 1, 2023
sahititarigoppula pushed a commit to OpsMx/deck-oes that referenced this pull request May 27, 2024
spinnaker#9971)

* feat(cloudRun): Implemented manifest stage for cloudRun

* feat(cloudRun): Incorporated suggested changes
sahititarigoppula pushed a commit to OpsMx/deck-oes that referenced this pull request May 31, 2024
spinnaker#9971)

* feat(cloudRun): Implemented manifest stage for cloudRun

* feat(cloudRun): Incorporated suggested changes
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
auto merged Merged automatically by a bot ready to merge Reviewed and ready for merge target-release/1.31
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants