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

validateBatchName should allow hyphens #2126

Merged
merged 1 commit into from
Nov 1, 2017

Conversation

Copy link
Contributor

@Ninir Ninir left a comment

Choose a reason for hiding this comment

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

LGTM! Nice catch, thanks @yzach 🚀 👍

@Ninir Ninir merged commit 3995266 into hashicorp:master Nov 1, 2017
@toddZilla0130
Copy link
Contributor

toddZilla0130 commented Nov 1, 2017

We also noticed this and I did a little more research into the matter, testing various edges when naming the 3 Batch resources. In addition to the above, I discovered that:

  • names must begin with an alphanumeric
  • job queues have the same naming rules as compute environments and job definitions.

The regex I came up with is this ^[0-9a-zA-Z]{1}[0-9a-zA-Z_\-]{0,127}$

and I added

ValidateFunc: validateBatchName,

to the name block of resourceAwsBatchJobQueue in resource_aws_batch_job_queue.go.

I had opened (and will close) this: #2108

but if you'd like me to follow up on the above with a new PR I will be happy to do so.

(The API docs for CreateJobQueue cite no naming restrictions but they most definitely exist.)

@ghost
Copy link

ghost commented Apr 10, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. Thanks!

@ghost ghost locked and limited conversation to collaborators Apr 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants