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: Allow specification of now --public in .drone.yml #2

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

atomdmac
Copy link

Allows users of the Drone plugin to specify the --public option as they would when using the now CLI directory. To do this, simply add the option to the .drone.yml file:

my_build_step:
  image: lucap/drone-now
  public: true
  ..other options...

Copy link
Owner

@lucaperret lucaperret left a comment

Choose a reason for hiding this comment

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

Could you also update the DOCS.md according to this change ?

Copy link
Owner

@lucaperret lucaperret left a comment

Choose a reason for hiding this comment

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

Could you improve the log concerning this option...

script.sh Outdated
# Is this a public deployment?
if [ "$PLUGIN_PUBLIC" == "true" ]
then
echo "> adding option --public"
Copy link
Owner

Choose a reason for hiding this comment

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

Could you be more precise ?
The documentation of the API can help.

Copy link
Author

Choose a reason for hiding this comment

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

What kind of precision are you looking for here? It seems obvious enough to me that the option corresponds to the now CLI given that this is a Drone plugin for precisely that. I'm happy to modify but I'm not clear on what other information you'd like to include here.

Copy link
Owner

@lucaperret lucaperret Mar 27, 2018

Choose a reason for hiding this comment

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

For every deployment done under the OSS plan, this needs to be set to true.

It could be good to inform the user that if he has a OSS plan, his source code and logs will be public, for example.

script.sh Outdated
echo "> adding option --public"
NOW_DEPLOY_OPTIONS="${NOW_DEPLOY_OPTIONS} --public"
else
echo "> --public option not specified"
Copy link
Owner

Choose a reason for hiding this comment

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

Precise the default value.

# Is this a public deployment?
if [ "$PLUGIN_PUBLIC" == "true" ]
then
echo "> adding option --public. If you are using an OSS plan, your source and logs will be public!"
Copy link
Owner

Choose a reason for hiding this comment

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

That is not true. In any case with this public option, the source and logs will be public...

configuring public deployment. Your source and logs will be public!

@@ -122,6 +122,17 @@ pipeline:
+ scale: 2
```

Example configuration for specifying the `--public` argument for the `now` CLI.
Copy link
Owner

Choose a reason for hiding this comment

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

Could you add this link for documentation : https://zeit.co/blog/now-public

deploy_name: deployment-name
secrets: [ now_token ]
- scale: 2
+ public: true
Copy link
Owner

Choose a reason for hiding this comment

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

Could you add this public property to the Parameter Reference section

@atomdmac atomdmac closed this Mar 27, 2018
@atomdmac atomdmac reopened this Mar 27, 2018
@lucaperret
Copy link
Owner

Hi @atomdmac, your feature request is quite interessant, could you complete the changes ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants