Join GitHub today
GitHub is home to over 40 million developers working together to host and review code, manage projects, and build software together.Sign up
Datatype for UID in fission-deployment-config.yaml #1232
We are using specs for doing all the deployments on fission.
With this approach when we deploy the incremental changes to PROD, it fails with duplicate resource error.
To overcome this, we are replacing the UID in fission-deployment-config.yaml with function name post specs are created.
Currently this approach is working for us.
$ cat fission-deployment-config.yaml.original apiVersion: fission.io/v1 kind: DeploymentConfig name: customer-status-csm uid: b16b8e4d-cb83-4197-8892-9cdaa7eb5a7f $ cat fission-deployment-config.yaml apiVersion: fission.io/v1 kind: DeploymentConfig name: customer-status-csm uid: test-function-name
BTW, may I ask how your workflow works?
Cause the original idea of
It would be great if you can share more information about how your pipeline works and other points that may help to increase the experience so that we can head in the right direction.
So far, I can only think of an issue that might be the problem:
Below is our high level workflow
Here only artifacts created in Point 1 are in version control system(GIT).