-
Notifications
You must be signed in to change notification settings - Fork 3
added grok rules and created logstack-shipper in dev #45
Conversation
This reverts commit 698ac79.
Fix localstack
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
--- | ||
name: dev-deploy | ||
|
||
on: | ||
push: | ||
branches: | ||
- development | ||
workflow_dispatch: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Do we want to setup similar things for staging and prod?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think that exists above in deploy.yml
, as far as I can tell. Would it be beneficial then to combine them and make environ
a variable?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Staging and prod setup are already included in the deploy.yml file. For debug purpose we separate development out so we may test/debug any changes push to development brunch first instead of master brunch.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This seems worthwhile to merge and road test in development. If we want to consolidate in the future, we can do so.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
changes for GSA/data.gov#4234