-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Configuration parameter stage
does not exist
#1909
Comments
Yes, you are correct. This is because |
Anton Medvedev <[email protected]> 於 2019年8月19日 週一 21:22 寫道:
… Yes, you are correct. This is because get('stage'). This is a bug. Can
you send fix PR?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#1909?email_source=notifications&email_token=AHFDEQNBY7BNG6TVZZ7CC3DQFKNB7A5CNFSM4IM7KMQ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4S5F6A#issuecomment-522572536>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AHFDEQPNAGM3EHQENX37NL3QFKNB7ANCNFSM4IM7KMQQ>
.
|
Hello there. I'm facing the same issue with
As it just prints configuration it should be only executed on the local machine, shouldn't it? |
My fix affected only the |
My bad. I misunderstood the fix and deploy behavior. All is fine. @dnaber-de |
Hello,
After upgrading from 6.4.3 to 6.5.0, I'm getting the error
Configuration parameter `stage` does not exist.
when deploying, whereconfig:current
is called.When I run
dep config:current
, I get the same error. It seems related to this commit: 6180366I have
default_stage
set to production. If I add to my host configuration, the stage attribute like this:The deployment goes through, but the
config:current
doesn't return anything:Am I missing something?
Regards
The text was updated successfully, but these errors were encountered: