This project is mirrored from https://gitlab.com/gitlab-org/build/omnibus-mirror/consul.git.
Pull mirroring failed .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
Last successful update .
Repository mirroring has been paused due to too many failed attempts. It can be resumed by a project maintainer or owner.
Last successful update .
- Dec 15, 2020
-
-
kaitlincarter-hc authored
-
kaitlincarter-hc authored
-
hashicorp-ci authored
-
John Cowen authored
-
John Cowen authored
In some circumstances this endpoint will have no results in it (dues to ACLs, Namespaces or filtering). This ensures that the response is at least an empty array (`[]`) rather than `null`
-
hashicorp-ci authored
-
John Cowen authored
-
hashicorp-ci authored
-
John Cowen authored
In order to test certain setups for our metrics visualizations we need to be able to setup several different `ui_config` settings during development/testing. Generally in the UI, we use the Web Inspector to set various cookie values to configure the UI how we need to see it whilst developing, so this PR: 1. Routes `ui_config` through a dev time only `CONSUL_UI_CONFIG` env variable so we can change it via cookies vars. 2. Adds `CONSUL_METRICS_PROXY_ENABLE`, `CONSUL_METRICS_PROVIDER` and `CONSUL_SERVICE_DASHBOARD_URL` so it's easy to set/unset these only values during development. 3. Adds an acceptance testing step so we can setup `ui_config` to whatever we want during testing. 4. Adds an async 'repository-like' method to the `UiConfig` Service so it feels like a repository - incase we ever need to get this via an HTTP API+blocking query. 5. Vaguely unrelated: we allow cookie values to be set via the location.hash whilst in development only e.g. `/ui/services#CONSUL_METRICS_PROXY_ENABLE=1` so we can link to different setups if we ever need to. All values added here are empty/falsey by default, so in order to see how it was previously you'll need to set the appropriate cookies values, but you can now also easily preview/test the the metrics viz in different/disabled states (with differing `ui_config`)
-
- Dec 14, 2020
-
-
R.B. Boyer authored
-
hashicorp-ci authored
-
John Cowen authored
* Add `Local` property to Datacenters * If you have not previous datacenter, redirect the user to the local dc * Add an `is-local` class to the local datacenter in the DC picker
-
John Cowen authored
* Reconfigure linting to be a node-test * Fixup linting across the project
-
hashicorp-ci authored
-
John Cowen authored
* Add service collections to get all ExternalServices * Add a basic collection helper * Use the collections to get all ExternalSources * Remove old Controllers
-
- Dec 11, 2020
-
-
Daniel Nephin authored
http: Check HTTPUseCache in a single place
-
s-christoff authored
-
Daniel Nephin authored
HTTPUseCache is only used is a gate for allowing QueryOptions.UseCache to be enabled. By moving it to the place where the query options are set, this behaviour is more obvious. Also remove parseInternal which was an alias for parse.
-
Daniel Nephin authored
testing: skip slow tests with -short
-
Maksym authored
-
hashicorp-ci authored
-
John Cowen authored
* ui: Controller dead code removal This commit removes a little code that became 'dead' as a result of previous PRs/commits * Remove a little more from the settings Controller * Remove CSS related to being able to set the dashboard_url in settings
-
hashicorp-ci authored
-
John Cowen authored
* install on-resize modifier * Rerrange things to use on-resize modifier for positioning
-
hashicorp-ci authored
-
John Cowen authored
-
- Dec 09, 2020
-
-
kaitlincarter-hc authored
* reorganize for clarity and update for value syntax * fix quotes around value * Apply suggestions from code review Co-authored-by:
Blake Covarrubias <blake@covarrubi.as> * Apply suggestions from code review Co-authored-by:
Freddy <freddygv@users.noreply.github.com> Co-authored-by:
Blake Covarrubias <blake@covarrubi.as> Co-authored-by:
Freddy <freddygv@users.noreply.github.com>
-
R.B. Boyer authored
Previously the tokens would fail to insert into the secondary's state store because the AuthMethod field of the ACLToken did not point to a known auth method from the primary.
-
Noel Quiles authored
* Update alert banner * Update expiration date for banner
-
hashicorp-ci authored
-
John Cowen authored
-
John Cowen authored
* Switch upstream-instances to use new style of searchable * Add search action to DataCollection plus basic README * Use DataCollection for PowerSelect searching in child-selectors * Remove old style filterable search for role/policies and instances * Remove old helpers/components related to search/sort/filter
-
hashicorp-ci authored
-
Kenia authored
* Refactor Stats and Series components * Remove unused variable from being passed down to Stats * Add item name to be passed down to Stats
-
hashicorp-ci authored
-
John Cowen authored
-
Daniel Nephin authored
docs: Add developer documentation and diagrams for streaming
-
Kenia authored
* create consul version metric with version label * agent/agent.go: add pre-release Version as well as label Co-Authored-By:
Radha13 <kumari.radha3@gmail.com> * verion and pre-release version labels. * hyphen/- breaks prometheus * Add Prometheus gauge defintion for version metric * Add new metric to telemetry docs Co-authored-by:
Radha Kumari <kumari.radha3@gmail.com> Co-authored-by:
Aestek <thib.gilles@gmail.com> Co-authored-by:
Daniel Nephin <dnephin@hashicorp.com>
-
hashicorp-ci authored
-
John Cowen authored
* Model layer changes to turn Node:ServiceInstances into hasMany We tried to make something that feels a little like ember-data yet not leave our approach of re-shaping the JSON directly from the response. 1. We added transformHasManyResponse for re-shaping JSON for hasMany relationships. we avoided the normalize word as ember-data serialize methods usually return something JSON:API shaped and we distinctly don't want to do that. Transform was the best word we could think of. 2. The integration tests across all of our models here feel very much like those types of tests that aren't really testing much, or assert too much to an extent that they get in the way rather than be of any use. I'd very much like to move a lot of this to unit tests. Currently most of the fingerprinting functionality is unit tested and these integration tests were originally to give confidence that IDs and related properties were being added correctly. 3. We've added a hasMany relationship, but not the corresponding belongsTo - yet at least. We don't require the belongsTo right now, and if we do we can add it later. * Integrate ServiceInstance search bar for Node:ServiceInstances * Hide Node.Meta when on the Node:ServiceINstance page We use a little string replace hack here for a human-like label, this is soon to be replaced with proper i10n replacement * Always ensure that a Namespace is set, and add comment explaining
-