Debian Codegraph @

docs/dyn/cloudbuild_v1.projects.locations.bitbucketServerConfigs.connectedRepositories.html

raw
1 <html><body>
2 <style>
3
4 body, h1, h2, h3, div, span, p, pre, a {
5 margin: 0;
6 padding: 0;
7 border: 0;
8 font-weight: inherit;
9 font-style: inherit;
10 font-size: 100%;
11 font-family: inherit;
12 vertical-align: baseline;
13 }
14
15 body {
16 font-size: 13px;
17 padding: 1em;
18 }
19
20 h1 {
21 font-size: 26px;
22 margin-bottom: 1em;
23 }
24
25 h2 {
26 font-size: 24px;
27 margin-bottom: 1em;
28 }
29
30 h3 {
31 font-size: 20px;
32 margin-bottom: 1em;
33 margin-top: 1em;
34 }
35
36 pre, code {
37 line-height: 1.5;
38 font-family: Monaco, 'DejaVu Sans Mono', 'Bitstream Vera Sans Mono', 'Lucida Console', monospace;
39 }
40
41 pre {
42 margin-top: 0.5em;
43 }
44
45 h1, h2, h3, p {
46 font-family: Arial, sans serif;
47 }
48
49 h1, h2, h3 {
50 border-bottom: solid #CCC 1px;
51 }
52
53 .toc_element {
54 margin-top: 0.5em;
55 }
56
57 .firstline {
58 margin-left: 2 em;
59 }
60
61 .method {
62 margin-top: 1em;
63 border: solid 1px #CCC;
64 padding: 1em;
65 background: #EEE;
66 }
67
68 .details {
69 font-weight: bold;
70 font-size: 14px;
71 }
72
73 </style>
74
75 <h1><a href="cloudbuild_v1.html">Cloud Build API</a> . <a href="cloudbuild_v1.projects.html">projects</a> . <a href="cloudbuild_v1.projects.locations.html">locations</a> . <a href="cloudbuild_v1.projects.locations.bitbucketServerConfigs.html">bitbucketServerConfigs</a> . <a href="cloudbuild_v1.projects.locations.bitbucketServerConfigs.connectedRepositories.html">connectedRepositories</a></h1>
76 <h2>Instance Methods</h2>
77 <p class="toc_element">
78 <code><a href="#batchCreate">batchCreate(parent, body=None, x__xgafv=None)</a></code></p>
79 <p class="firstline">Batch connecting Bitbucket Server repositories to Cloud Build.</p>
80 <p class="toc_element">
81 <code><a href="#close">close()</a></code></p>
82 <p class="firstline">Close httplib2 connections.</p>
83 <h3>Method Details</h3>
84 <div class="method">
85 <code class="details" id="batchCreate">batchCreate(parent, body=None, x__xgafv=None)</code>
86 <pre>Batch connecting Bitbucket Server repositories to Cloud Build.
87
88 Args:
89 parent: string, The name of the `BitbucketServerConfig` that added connected repository. Format: `projects/{project}/locations/{location}/bitbucketServerConfigs/{config}` (required)
90 body: object, The request body.
91 The object takes the form of:
92
93 { # RPC request object accepted by BatchCreateBitbucketServerConnectedRepositories RPC method.
94 &quot;requests&quot;: [ # Required. Requests to connect Bitbucket Server repositories.
95 { # Request to connect a repository from a connected Bitbucket Server host.
96 &quot;bitbucketServerConnectedRepository&quot;: { # / BitbucketServerConnectedRepository represents a connected Bitbucket Server / repository. # Required. The Bitbucket Server repository to connect.
97 &quot;parent&quot;: &quot;A String&quot;, # The name of the `BitbucketServerConfig` that added connected repository. Format: `projects/{project}/locations/{location}/bitbucketServerConfigs/{config}`
98 &quot;repo&quot;: { # BitbucketServerRepositoryId identifies a specific repository hosted on a Bitbucket Server. # The Bitbucket Server repositories to connect.
99 &quot;projectKey&quot;: &quot;A String&quot;, # Required. Identifier for the project storing the repository.
100 &quot;repoSlug&quot;: &quot;A String&quot;, # Required. Identifier for the repository.
101 &quot;webhookId&quot;: 42, # Output only. The ID of the webhook that was created for receiving events from this repo. We only create and manage a single webhook for each repo.
102 },
103 &quot;status&quot;: { # The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors). # Output only. The status of the repo connection request.
104 &quot;code&quot;: 42, # The status code, which should be an enum value of google.rpc.Code.
105 &quot;details&quot;: [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.
106 {
107 &quot;a_key&quot;: &quot;&quot;, # Properties of the object. Contains field @type with type URL.
108 },
109 ],
110 &quot;message&quot;: &quot;A String&quot;, # A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client.
111 },
112 },
113 &quot;parent&quot;: &quot;A String&quot;, # Required. The name of the `BitbucketServerConfig` that added connected repository. Format: `projects/{project}/locations/{location}/bitbucketServerConfigs/{config}`
114 },
115 ],
116 }
117
118 x__xgafv: string, V1 error format.
119 Allowed values
120 1 - v1 error format
121 2 - v2 error format
122
123 Returns:
124 An object of the form:
125
126 { # This resource represents a long-running operation that is the result of a network API call.
127 &quot;done&quot;: True or False, # If the value is `false`, it means the operation is still in progress. If `true`, the operation is completed, and either `error` or `response` is available.
128 &quot;error&quot;: { # The `Status` type defines a logical error model that is suitable for different programming environments, including REST APIs and RPC APIs. It is used by [gRPC](https://github.com/grpc). Each `Status` message contains three pieces of data: error code, error message, and error details. You can find out more about this error model and how to work with it in the [API Design Guide](https://cloud.google.com/apis/design/errors). # The error result of the operation in case of failure or cancellation.
129 &quot;code&quot;: 42, # The status code, which should be an enum value of google.rpc.Code.
130 &quot;details&quot;: [ # A list of messages that carry the error details. There is a common set of message types for APIs to use.
131 {
132 &quot;a_key&quot;: &quot;&quot;, # Properties of the object. Contains field @type with type URL.
133 },
134 ],
135 &quot;message&quot;: &quot;A String&quot;, # A developer-facing error message, which should be in English. Any user-facing error message should be localized and sent in the google.rpc.Status.details field, or localized by the client.
136 },
137 &quot;metadata&quot;: { # Service-specific metadata associated with the operation. It typically contains progress information and common metadata such as create time. Some services might not provide such metadata. Any method that returns a long-running operation should document the metadata type, if any.
138 &quot;a_key&quot;: &quot;&quot;, # Properties of the object. Contains field @type with type URL.
139 },
140 &quot;name&quot;: &quot;A String&quot;, # The server-assigned name, which is only unique within the same service that originally returns it. If you use the default HTTP mapping, the `name` should be a resource name ending with `operations/{unique_id}`.
141 &quot;response&quot;: { # The normal, successful response of the operation. If the original method returns no data on success, such as `Delete`, the response is `google.protobuf.Empty`. If the original method is standard `Get`/`Create`/`Update`, the response should be the resource. For other methods, the response should have the type `XxxResponse`, where `Xxx` is the original method name. For example, if the original method name is `TakeSnapshot()`, the inferred response type is `TakeSnapshotResponse`.
142 &quot;a_key&quot;: &quot;&quot;, # Properties of the object. Contains field @type with type URL.
143 },
144 }</pre>
145 </div>
146
147 <div class="method">
148 <code class="details" id="close">close()</code>
149 <pre>Close httplib2 connections.</pre>
150 </div>
151
152 </body></html>