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.

Sign up for GitHub

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

Jump to bottom

coab instances deployment name RFC-1123 compatibility #299

Open
JCL38-ORANGE opened this issue Jun 18, 2020 · 1 comment
Open

coab instances deployment name RFC-1123 compatibility #299

JCL38-ORANGE opened this issue Jun 18, 2020 · 1 comment
Assignees
@JCL38-ORANGE
Labels
enhancement

Comments

@JCL38-ORANGE
Copy link
Contributor

JCL38-ORANGE commented Jun 18, 2020 •
edited
Loading

Expected behavior

bosh deployment name generated by COAB must be compliant with RFC-1123

Observed behavior

bosh deployment name generated by COAB are not compliant with RFC-1123 ("_" character is not valid)

Solution outline

Add the possibility to configure separator used between deployment prefix and deployment id (service guid). For a m prefix and "uuid"

  • default and existing services => m_uuid
  • new services with deployment.model-deployment-separator: "-" => m-uuid
@JCL38-ORANGE JCL38-ORANGE self-assigned this Jun 18, 2020
@JCL38-ORANGE
Copy link
Contributor Author

will be embedded in v0.30

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JCL38-ORANGE JCL38-ORANGE

Labels
enhancement
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@poblin-orange @JCL38-ORANGE