`PUT` використовується для отримання даних, які мають замінити чинні дані.

### Попередження про заміну

Це означає, що якщо Ви хочете оновити елемент `bar`, використовуючи `PUT` з тілом:

```Python
{
    "name": "Barz",
    "price": 3,
    "description": None,
}
```

оскільки він не містить вже збереженого атрибута `"tax": 20.2`, модель введення прийме значення за замовчуванням `"tax": 10.5`.

						</div>
					</div>
					<div class="text-center">
						<la:link href="/"
							styleClass="btn btn-default">
							<em class="fa fa-arrow-circle-left">
							<la:message key="labels.profile.back" />
						</la:link>
						<button type="submit" name="changePassword"
							class="btn btn-success"
							value="<la:message key="labels.profile.update"/>">
							<em class="fa fa-pencil-alt">

    void parseSetsMechanismToken() throws IOException {
        TestSpnegoToken t = new TestSpnegoToken();
        byte[] raw = new byte[] { 5, 6 };
        t.parse(raw);
        assertTrue(t.isParsed(), "parse should mark parsed");
        assertArrayEquals(raw, t.getMechanismToken(), "parse should set mechanismToken");
    }

    @Test
    @DisplayName("parse throws IOException on null input")
    void parseThrowsOnNull() {

                            <div class="card-footer">
                                <c:if test="${crudMode == 4}">
                                    <button type="submit" class="btn btn-default" name="back"
                                            value="<la:message key="labels.crawling_info_button_back" />">
                                        <em class="fa fa-arrow-circle-left">

 limitations under the License.
-->
Contributing to Apache Maven
======================

You have found a bug or you have an idea for a cool new feature? Contributing
code is a great way to give something back to the open source community. Before
you dig right into the code, there are a few guidelines that we need
contributors to follow so that we can have a chance of keeping on top of
things.

     */
    @Test
    void testCreateExactMatcher() {
        RequirementMatcher matcher;
        matcher = RequirementMatcherFactory.createExactMatcher("foo");
        assertFalse(matcher.matches("bar"));
        assertFalse(matcher.matches("foobar"));
        assertFalse(matcher.matches("foob"));
        assertTrue(matcher.matches("foo"));
    }

    /**

                                </table>
                            </div>
                            <div class="card-footer">
                                <button type="submit" class="btn btn-default" name="list" value="back">
                                    <em class="fa fa-arrow-circle-left">
                                    <la:message key="labels.crud_button_back"/>
                                </button>

* key (as in key-value pair, dictionary key): clave
* array (as in JSON array): array
* API key: API key (do not translate to "clave API")
* 100% test coverage: cobertura de tests del 100%
* back and forth: de un lado a otro
* I/O (as in "input and output"): I/O (do not translate to "E/S")
* Machine Learning: Machine Learning (do not translate to "Aprendizaje Automático")

The way to describe this in OpenAPI, is to mark that field as **required**, because it will always be there.

Because of that, the JSON Schema for a model can be different depending on if it's used for **input or output**:

4. If you want *faster* PR reviews, read how: https://git.k8s.io/community/contributors/guide/pull-requests.md#best-practices-for-faster-reviews
5. If the PR is unfinished, see how to mark it: https://git.k8s.io/community/contributors/guide/pull-requests.md#marking-unfinished-pull-requests
-->

#### What type of PR is this?

<!--
Add one of the following kinds:
/kind bug
/kind cleanup