Skip to content
This repository has been archived by the owner on Apr 18, 2021. It is now read-only.

Jay/add choice to add registry #38

Merged
merged 2 commits into from
Jan 9, 2019
Merged

Conversation

JhChoy
Copy link
Contributor

@JhChoy JhChoy commented Jan 8, 2019

PR Checklist

Please check if your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Issue Number: #33

What is the new behavior?

When you are trying to deploy just nonUpgradeable contracts without Registry, you can set like this:

  "registry": false,

at service.vvisp.json.

Does this PR introduce a breaking change?

  • Yes
  • No

@JhChoy JhChoy added enhancement New feature or request feature: deploy-service labels Jan 8, 2019
@JhChoy JhChoy self-assigned this Jan 8, 2019
@JhChoy JhChoy added the config About config files(service.vvisp.json, state.vvisp.json, .env etc) label Jan 8, 2019
@JhChoy JhChoy merged commit 278462b into dev Jan 9, 2019
@JhChoy JhChoy deleted the jay/add-choice-to-add-registry branch January 9, 2019 06:50
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
config About config files(service.vvisp.json, state.vvisp.json, .env etc) enhancement New feature or request feature: deploy-service
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant