aboutsummaryrefslogtreecommitdiffstats
path: root/config-model-api/src/main/java/com/yahoo/config/application/api/Endpoint.java
Commit message (Collapse)AuthorAgeFilesLines
* Update copyrightJon Bratseth2023-10-091-1/+1
|
* Complete bcp handlingJon Bratseth2023-02-191-1/+1
| | | | | - Add bcp to schema validation - Read endpoints defined in bcp elements
* Set private DNS for existing VPC endpoints servicesjonmv2022-11-241-5/+7
|
* Allow multiple regions and instances in application endpoints, part XMLjonmv2022-10-191-8/+6
|
* Support application-level endpoints in DeploymentSpecMartin Polden2021-11-021-21/+115
|
* CleanupMartin Polden2021-11-021-5/+5
|
* Update 2020 Oath copyrights.gjoranv2021-10-271-1/+1
|
* Add/corect copyright headersJon Bratseth2020-01-031-0/+1
|
* Require validation override for destructive endpoint changesMartin Polden2019-10-171-2/+9
|
* Default to all declared prod zones for endpoints without regionsØyvind Grønnesby2019-07-081-0/+3
| | | | | | - Extract all production zones in the DeploymentSpec constructor and update all Endpoints instances without regions to these zones - Add more tests to validate that this does what we want it to.
* Update javadoc to explain new behavior on default endpoint IDØyvind Grønnesby2019-06-271-1/+1
|
* Change default endpoint-id to be "default"Øyvind Grønnesby2019-06-261-1/+2
| | | | | | | | | | | | | | | | Previously this defaulted to the value of the container-id, but using "default" makes the feature behave more closely to the existing global-service-id feature. Previously you needed to write: <endpoint endpoint-id="default" container-id="qrs" /> to mirror the existing behavior. Now you can do <endpoint container-id="qrs" /> to get the same behavior.
* Improve validation of endpoint IDsMartin Polden2019-06-061-2/+22
| | | | | Same validation rules that are in place for `<rotations/>' in `services.xml`, which we are removing.
* Have Endpoint use RegionName instead of a StringØyvind Grønnesby2019-05-311-3/+9
|
* Add endpoints to deployment specificationØyvind Grønnesby2019-05-291-0/+51
Endpoints are now part of the DeploymentSpec and understood by the DeploymentSpecXmlReader classes.