Skip to content
Snippets Groups Projects
Select Git revision
  • dbiryukov_populate_projects_with_pipeline_variables_mr-499491
  • 477783-use-segmented-export-for-project-and-instance-level-vulnerability-exports
  • jay-update-vault-setup-docs
  • tbulva-darkmode-regex-design-token
  • 451588-remove-vuex-create-update-actions
  • 474946-update-relationship-icons-on-boards
  • saf-add-policy-rules-for-organizational-cluster-agents
  • Remove-Orphaned-Vulnerability-Notes
  • 521971-variables-inputs-banner
  • master default protected
  • issue_509317
  • 515973-dast-docs-timeout-explanation-diagram
  • kkwentus-update-workflow-install
  • mermaid-copy-clipboard
  • 418827-expand-diff
  • adjust-feature-settings-mutation
  • 521383-add-feature-flag-model-upgrade-summarize-code-review
  • ingest_and_display_direct_dependencies
  • irinabron/521739-pg-stat-statements
  • prevent-submitting-when-non-csv-file-selected-on-front-end
  • v17.7.6-ee protected
  • v17.8.4-ee protected
  • v17.9.1-ee protected
  • v17.8.3-ee protected
  • v17.7.5-ee protected
  • v17.9.0-ee protected
  • v17.9.0-rc42-ee protected
  • v17.6.5-ee protected
  • v17.7.4-ee protected
  • v17.8.2-ee protected
  • v17.6.4-ee protected
  • v17.7.3-ee protected
  • v17.8.1-ee protected
  • v17.8.0-ee protected
  • v17.7.2-ee protected
  • v17.8.0-rc42-ee protected
  • v17.5.5-ee protected
  • v17.6.3-ee protected
  • v17.7.1-ee protected
  • v17.7.0-ee protected
40 results

.gitignore

  • Sean McGivern's avatar
    b3c5c996
    Simplify adding new Redis instance · b3c5c996
    Sean McGivern authored
    The main sticking point was `config/README.md`, which went into a lot of
    detail about each instance. It was quite easy to make a copy and paste
    error, as some instances had default URLs and others didn't, some had
    fallback instances and others didn't, etc.
    
    This changes a number of things:
    
    1. `config/README.md` now has a table for the Redis instances with a
       single list of instructions that apply to all instances.
    2. There are now specs to ensure that each Redis instance has a default
       URL set when no Redis config at all is present.
    3. Instances that use a fallback instance for config will automatically
       use the default URL of their fallback instance. They should not
       define their own default URL.
    4. The `.gitignore` file does not need to be updated for each new Redis
       instance.
    5. The example config files are now gone as `request.yml.example` should
       be sufficient.
    Verified
    b3c5c996
    History
    Simplify adding new Redis instance
    Sean McGivern authored
    The main sticking point was `config/README.md`, which went into a lot of
    detail about each instance. It was quite easy to make a copy and paste
    error, as some instances had default URLs and others didn't, some had
    fallback instances and others didn't, etc.
    
    This changes a number of things:
    
    1. `config/README.md` now has a table for the Redis instances with a
       single list of instructions that apply to all instances.
    2. There are now specs to ensure that each Redis instance has a default
       URL set when no Redis config at all is present.
    3. Instances that use a fallback instance for config will automatically
       use the default URL of their fallback instance. They should not
       define their own default URL.
    4. The `.gitignore` file does not need to be updated for each new Redis
       instance.
    5. The example config files are now gone as `request.yml.example` should
       be sufficient.
Code owners
Assign users and groups as approvers for specific file changes. Learn more.