update fork #1
Merged
update fork #1
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
* add captains log * update infographic * Implement syntax suggestions from Travis * shorten traj copy and put above graphic, keeping it above fold * add clarifying subtitle good for SEO * remove unused image refs in head matter * Update community/captains-log/index.md Co-Authored-By: Dave Dorbin <ddorbin@google.com> * add doc to repos description Co-authored-by: Dave Dorbin <ddorbin@google.com> Co-authored-by: brian-armory <53799971+brian-armory@users.noreply.github.com>
* update intro and add analyses to events graph * add analysis and values to data visualization explanations * fix img title case * syntax edits
* Clarify artifact format usage with spin CLI * Update reference/artifacts/index.md Co-Authored-By: Dave Dorbin <ddorbin@google.com> * Update reference/artifacts/index.md Co-Authored-By: Dave Dorbin <ddorbin@google.com> * Update index.md Co-authored-by: Dave Dorbin <ddorbin@google.com>
#1703 Co-authored-by: Travis Tomsu <ttomsu@google.com>
* chore(kubernetes): link to v1 provider removal rfc * chore(kubernetes): replace link to clouddriver at master with hash * chore(kubernetes): replace v2 setup link with reference link Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
…ifications (#1711) * docs(managed-delivery): Document ability to use interactive Slack notifications * Address review feedback + minor improvements
Fixes the least important part of spinnaker/spinnaker#5483
At this stage in the Managed Delivery Getting Started Guide, this is a gentle reminder of the endpoint that should be used to see all of the possible values of the `AWS_ACCOUNT_NAME` placeholder. Co-authored-by: Emily Burns <emburns@netflix.com>
Bumps [nokogiri](https://github.com/sparklemotion/nokogiri) from 1.10.5 to 1.10.8. - [Release notes](https://github.com/sparklemotion/nokogiri/releases) - [Changelog](https://github.com/sparklemotion/nokogiri/blob/master/CHANGELOG.md) - [Commits](sparklemotion/nokogiri@v1.10.5...v1.10.8) Signed-off-by: dependabot[bot] <support@github.com>
changed ref-style link names Signed-off-by: Aimee Ukasick <aimeeu.opensource@gmail.com>
* docs(submitting): add more info around the RFC process * Update community/contributing/submitting.md Co-Authored-By: Dave Dorbin <ddorbin@google.com> * Update community/contributing/submitting.md Co-Authored-By: Dave Dorbin <ddorbin@google.com> * Update community/contributing/submitting.md Co-Authored-By: Dave Dorbin <ddorbin@google.com> Co-authored-by: Dave Dorbin <ddorbin@google.com>
…viousClass for Orca DualExecutionRepository (#1700) "com.netflix.spinnaker.orca.sql.telemetry.SqlInstrumentedExecutionRepository" was already deleted and currently using class name for DualExecutionRepository doesn't work because of spinnaker/spinnaker#5381 It's better to use bean name now. Co-authored-by: brian-armory <53799971+brian-armory@users.noreply.github.com> Co-authored-by: Rob Zienert <rob@robzienert.com>
Updates the requirements on [rake](https://github.com/ruby/rake) to permit the latest version. - [Release notes](https://github.com/ruby/rake/releases) - [Changelog](https://github.com/ruby/rake/blob/master/History.rdoc) - [Commits](ruby/rake@v10.5.0...v12.3.3) Signed-off-by: dependabot[bot] <support@github.com>
* fix(plugins): updating plugin documentation for pf4j
…key off github action build (#1753)
Co-authored-by: Travis Tomsu <ttomsu@google.com>
update the "add REPOSITORY" command. it needs the raw content
…1758) The mergify config currently doesn't distinguish between merging to master and merging to a release branch. It currently never merges to release branches because mergify doesn't have permission to merge to these branches (due to branch protection rules). I don't want to give mergify that permission without updating the config file here, as then it would merge to release branches after any approval, whereas we only want to merge to release branches if a PR is approved by a release manager. This updates the mergify config to scope the existing rules to only apply to the master branch, and adds a new rule to merge to release branches upon approval by a release manager. Because the 1.17 branch (and likely the 1.18 branch in some repos) is still exclusively using Travis CI instead of github actions, also add a rule the merges if Travis CI passes to account for these branches. This rule can be deleted once all of the active branches in the repo are using Github actions. Co-authored-by: Michael Plump <plumpy@google.com>
I accidentally re-released 1.19.2; revert the change to the docs so the release time stays correct (and so that the extra deprecated on 1.19.1 goes away). This reverts commit 51a7e74.
The documentation mentioned that the Jenkins master should be set up using a user's password. It turns out that the API key should be used instead. This commit changes the documentation to reflect that. Co-authored-by: Michael Plump <plumpy@google.com>
* Updating settings.js code Based off this issue, setting the settings.js configuration to the new setting helped us in our email notifications. Deck was broken until we applied this change. spinnaker/spinnaker#2484 (comment) * Updating to settings-local.js * Update setup/features/notifications/index.md Co-Authored-By: Eric Zimanyi <ezimanyi@google.com> Co-authored-by: Eric Zimanyi <ezimanyi@google.com>
in section Enable your custom provider by following an error was coming. Was passed main parameter 'hal' but no main parameter was defined in your arg class I fixed it by separating in 2 steps 1-Configure the parameters 2-Enable the oauth2 feature with `authn oauth2 enable`
First pass of these docs for the first gardening day. We'll iterate as people try it out for this and subsequent gardening days.
dorbin
added a commit
that referenced
this pull request
Jul 23, 2020
Co-authored-by: Dave Dorbin <ddorbin@google.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
update fork