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

Regression: cannot provide human-readable site name #157

Closed
mojodna opened this issue Oct 18, 2018 · 4 comments · Fixed by #4327
Closed

Regression: cannot provide human-readable site name #157

mojodna opened this issue Oct 18, 2018 · 4 comments · Fixed by #4327
Labels
area: command: deploy area: dx good first issue type: feature code contributing to the implementation of a feature and/or user facing functionality

Comments

@mojodna
Copy link

mojodna commented Oct 18, 2018

With the previous version of the CLI, I was deploying to a specific site using

netlify deploy -p dist/ -s planet-stac

With the new version of the CLI, I now need to use

netlify deploy --prod --dir dist/ --site 95a54956-1c9b-4548-87bc-<redacted>

Is it possible to use the human-readable name when deploying sites using the new CLI?

@bcomnes
Copy link
Contributor

bcomnes commented Oct 24, 2018

Possibly. Is this for a more readable CI script? When used interactively, the ideas is once you are logged in, and your local folder is linked to a site, netlify deploy is useful without any flags.

@bcomnes
Copy link
Contributor

bcomnes commented Oct 24, 2018

I looked into this some more, and this should be easier than I expected. We can add this back.

@mojodna
Copy link
Author

mojodna commented Oct 25, 2018

It's for a repo that's deployed to multiple sites to visualize different datasets: https://github.com/radiantearth/stac-browser/blob/master/package.json#L12-L14

It's not linked to a single site as a result, and having readable names makes it easier for new people to understand/use.

Thanks!!

@MichalBryxi
Copy link

Also note that it's currently confusing in the documentation, because in various places (and possibly blog posts) it reads:

site (option) - A site ID to deploy to

But on the netlify web: https://app.netlify.com/sites/{myapp}/settings/general the closest to site id I can find is site name, which worked till now. Second best guess is API ID, which is actually correct.

And when you provide wrong ID netlify-cli just spits out:

 netlify deploy
 ›   Error: Not Found

Without any possibility to figure out what's wrong. At least I haven't found --verbose or --debug flag for it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: command: deploy area: dx good first issue type: feature code contributing to the implementation of a feature and/or user facing functionality
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants